docs(rfc): add RFC-000.0001 Flutter Architecture & Reference Taxonomy - #1
Conversation
Establish the architecture taxonomy, numbering scheme, and lifecycle process for Flutter Requests for Comments (RFCs). - Introduce structured identifier format `RFC-AAA.NNN` across 8 core domains (000 Meta through 700 Documentation & Ecosystem). - Define file naming (`rfc/AAA.NNN-kebab-case.md`) and YAML frontmatter schema. - Outline a 4-step assignment lifecycle using `.000` draft placeholders to prevent number collisions during proposal phases. - Specify rules for cross-cutting proposals and number immutability.
|
Would be nice to have "WANT_LGTM: <list|all>" |
|
We should also consider OKF if we ever wanted to hook these up to a harness. |
zanderso
left a comment
zanderso
left a comment
There was a problem hiding this comment.
This is a great start. For a complete RFC process we'll also need RFCs that specify the review process, similar to what Slava has in his CL.
I welcome another RFC after this one, appropriately numbered, to cover the review process. Issue #3 |
Leave optional mailbox format
jtmcdole
changed the title
|
Updated to latest requests. Note: this repo current has a requirement for 2-approvals before submitting. |
Piinks
left a comment
Piinks
left a comment
There was a problem hiding this comment.
Updated to latest requests. Note: this repo current has a requirement for 2-approvals before submitting.
Roger, Roger. LGTM
3 participants
Establish the architecture taxonomy, numbering scheme, and lifecycle process for Flutter Requests for Comments (RFCs).
AAA.NNNacross 8 core domains (000 Meta through 700 Documentation & Ecosystem).rfc/AAA.NNN-kebab-case.md) and YAML frontmatter schema..000draft placeholders to prevent number collisions during proposal phases.OKFdocument headers for later adoption.fixes: #2